Methods and systems for provisioning payment credentials

ABSTRACT

A method and system for provisioning payment credentials usable by a mobile device in conducting a payment. The method is conducted at a provisioning system and comprises the steps of: receiving payment credentials from a receiving device, the payment credentials having been obtained from a portable payment device presented by a consumer at the receiving device; receiving, from the receiving device, an identifier entered by the consumer; identifying a mobile device or a secure element corresponding to the identifier; and communicating the payment credentials or a derivation of the payment credentials to the identified mobile device or the secure element to be securely stored in association with the mobile device. The method may include: encrypting the received payment credentials, the encrypted payment credentials having a unique decryption key; and wherein communicating a derivation of the payment credentials communicates the unique decryption key.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application claims priority from, and incorporates by reference,U.S. Provisional Patent Application No. 61/823,840 filed on 15 May 2013entitled “Mobile Device Provisioning Kiosk”, South African ProvisionalPatent Application No. 2013/03719 filed on 22 May 2013 entitled“Provisioning Payment Credentials to a Mobile Device” and South AfricanProvisional Patent Application No. 2013/06249 filed on 20 Aug. 2013entitled “Provisioning Payment Credentials to a Remotely AccessibleServer”.

FIELD OF INVENTION

This application relates to the field of provisioning paymentcredentials usable by a mobile device.

BACKGROUND

As more merchants are adopting of point-of-sale terminals that arecapable of conducting transactions with mobile devices, consumers aremore and more likely to replace their physical wallets with digitalwallet applications running on their mobile devices (e.g., mobilephones). Transactions with digital wallet applications running on amobile device may be contactless, for example, using near fieldcommunication (NFC) capabilities of the mobile device.

Contactless payment transactions provide significant convenience toconsumers as they allow consumers to make purchases more quickly andconveniently than in a contact-based environment. In a contactlesspayment transaction, a consumer brings a contactless enabled consumerportable payment device (CPPD) such as a contactless smart card or amobile phone in close proximity with an acceptance terminal. Informationsuch as payment credentials is exchanged between the contactless CPPDand the acceptance terminal in a wireless manner to carry out thepayment transaction without requiring direct physical contact betweenthe contactless CPPD and the acceptance terminal. In some cases, thecontactless CPPD and the acceptance terminal are not collocated, but mayrather be in different locations, for example, in different cities orcountries. In such a case the information is transmitted between thecontactless CPPD and the acceptance terminal via, for example, theInternet.

It is often required by various standards or compliance authorities thata mobile device being employed as a contactless CPPD contains a secureelement. Such a secure element is not unlike a secure integrated circuitused in conventional CPPDs, such as secure integrated circuit creditcards. The secure elements which are in communication with the mobiledevices typically provide a secure memory and secure processor which areseparate from the mobile device memory and processor and can only beaccessed by trusted applications, often only after a specified personalidentification number (PIN) has been correctly entered. The mobiledevices in which such secure elements are disposed or embedded are oftenequipped with proximity communications interfaces such as, for example,near field communications (NFC).

It is in this secure memory that information, such as paymentcredentials, may be stored. In some cases, the provisioning of suchpayment credentials to the secure memory of the mobile device may be viaover-the-air (OTA) communications methods originating from a trustedservice manager (TSM). Such TSMs are typically operated from secure datacenters such that the process meets security standards imposed byrelevant standards or compliance authorities.

Provisioning digital wallet applications on mobile devices can be acumbersome task. For example, in order to provision a mobile device withthe credentials to conduct contactless transactions such as contactlesspayment transactions, users may be required to access a contactlesstransaction service provider from their mobile device to carry out anOTA provisioning process. The provisioning process may require the userto manually enter user credentials such as account numbers. As mostconsumers likely have many credential storage instruments such ascredit/debit cards from different banks that the user would like toinclude in the digital wallet application, entering this information forall credential storage instruments of a user can be a time consumingprocess. Furthermore, the OTA provisioning process may incur undesirablewireless data usage charges for the user.

Embodiments of the invention aim to address these and other problemsindividually and collectively, at least to some extent.

BRIEF SUMMARY

According to a first aspect of the present invention there is provided amethod for provisioning payment credentials usable by a mobile device inconducting a payment, the method being conducted at a provisioningsystem and comprising the steps of: receiving payment credentials from areceiving device, the payment credentials having been obtained from aportable payment device presented by a consumer at the receiving device;receiving, from the receiving device, an identifier entered by theconsumer; identifying a mobile device or a secure element associatedwith the mobile device corresponding to the identifier; andcommunicating the payment credentials or a derivation of the paymentcredentials to the identified mobile device or the secure element to besecurely stored in association with the mobile device.

The method may additionally include: encrypting the received paymentcredentials, the encrypted payment credentials having a uniquedecryption key. The payment credentials may be communicated in encryptedform with the unique decryption key being stored at the provisioningsystem. In one embodiment, communicating a derivation of the paymentcredentials communicates the unique decryption key and the encryptedpayment credentials are stored at the provisioning system. In the casewhere the unique decryption key is communicated, the unique decryptionkey may be purged from the provisioning system.

In embodiments of the method, the provisioning system is a remotelyaccessible server of an issuing authority, a security gateway, ortrusted service manager, and wherein communicating the paymentcredentials or a derivation of the payment credentials to the identifiedmobile device or the secure element uses a secure channel ofcommunication.

In alternative embodiments of the method, the provisioning system is akiosk having a processor local to the receiving device, and wherein themethod includes: establishing a communication channel between the kioskand the mobile device for communicating the payment credentials or aderivation of the payment credentials. The kiosk may act as anintermediary for a remotely accessible server and the method mayincludes using the received identifier to identify and/or verify a useror account at a remotely accessible server.

The method may include: requesting authorization from a trusted servicemanager to access a secure element; and receiving a security key toaccess the secure element.

The method may further include: communicating additional credentials tothe identified mobile device or the secure element to be securely storedin association with the mobile device, wherein the additionalcredentials are required in use in addition to the payment credentialsor derivation of the payment credentials to carry out a transaction. Inone embodiment, the additional credentials may be card verificationvalues. In another embodiment, the additional credentials may be in theform of a dynamic verification application or algorithm for generatingdynamic verification values. The method may include obtaining theadditional credentials from a remotely accessible server using theidentifier and forwarding the additional credentials to the mobiledevice.

The receiving device may be one of the group of: a card readerassociated with a kiosk, a point of sales device, an automated tellermachine, a merchant point of sales terminal, or a personal PIN entrydevice (PPED).

The portable payment device may be one of the group of: a magneticstripe credit or debit card, a security integrated circuit credit ordebit card, a bank card, a contactless bank card, a voucher card, anexisting payment credential stored on a mobile device.

The received payment credentials may include receiving one or more oftrack 1 data, track 2 data, track 3 data and track 2 equivalent data.The received payment credentials may include one or more of the groupof: track data, an account number, account holder name and/or date ofbirth, a bank identification number (BIN), a primary account number(PAN), a service code, an expiration date, card verification values(CVV1 or CVV2), personal details of an account holder, a PIN block oroffset, a bank account number, a branch code, a loyalty account numberor identifier, credit and/or debit card number information, accountbalance information.

The identifier may be one or more of the group of: a mobile stationinternational subscriber directory number (MSISDN), an email address, asocial network identifier, a predefined consumer name, a consumeraccount number.

The step of receiving payment credentials and the step of receiving anidentifier may include receiving a single secure transaction messagecontaining the payment credentials and the identifier. The securetransaction message may be one of the group of: a payment processingnetwork message, a financial transaction message, a financialtransaction message in the form of an ISO8583 message, a financialtransaction message containing a server routing code. The server routingcode may be used to route the financial transaction message to theremotely accessible server by a payment processing network.

Identifying a mobile device or a secure element corresponding to theidentifier may include: determining whether or not a mobile device orsecure element corresponding to the identifier has been registered witha remotely accessible server and, if the mobile device or has beenregistered, identifying a corresponding communication address of themobile device and/or secure element.

Further features provide for the step of identifying a mobile devicecorresponding to the identifier to include the step of using theidentifier to query a database so as to obtain a communication addressof the mobile device associated with the identifier. Further featuresprovide for the step of communicating the payment credentials to themobile device to include communicating the payment credentials to themobile device using the communication address.

Communicating the payment credentials or a derivation of the paymentcredentials to the identified mobile device to be securely stored inassociation with the mobile device, may include: communicating thepayment credentials or a derivation of the payment credentials to themobile device to be stored in a secure element, wherein the secureelement is one of the group of: a secure element provided in the mobiledevice, a secure element embedded in a layer which sits between acommunication component of the mobile device and a communicationcomponent interface of the mobile device, a secure element provided in acommunication component of the mobile device, a cloud-based secureelement associated with the mobile device. In one embodiment, the secureelement may be embedded in a label, card or tray and which sits inbetween a communication component of the mobile device and acommunication component interface of the mobile device.

The method may be repeated for multiple payment credentials to besecurely stored in association with a single mobile device.

The method may be used for transferring payment credentials to a secondmobile device from their existing secure storage on a first mobiledevice, wherein the portable payment device is an existing paymentcredential securely stored on the first mobile device.

According to second aspect of the present invention there is provided amethod for provisioning payment credentials usable by a mobile device inconducting a payment, the method being conducted at a point of salesdevice and comprising the steps of: obtaining payment credentials from aportable payment device presented by a consumer at a receiving device;receiving an identifier entered by the consumer into the point of salesdevice; communicating the payment credentials and identifier to aremotely accessible server for further communication of the paymentcredentials or a derivation of the payment credentials to a mobiledevice or a secure element to be securely stored in association with themobile device.

According to a third aspect of the present invention there is provided asystem for provisioning payment credentials usable by a mobile device inconducting a payment, including a provisioning system comprising: apayment credentials receiver for receiving payment credentials from areceiving device, the payment credentials having been obtained from aportable payment device presented by a consumer at the receiving device;an identifier receiver for receiving, from the receiving device, anidentifier entered by the consumer; an identifying component foridentifying a mobile device or a secure element associated with themobile device corresponding to the identifier; and a communicationmodule for communicating the payment credentials or a derivation of thepayment credentials to the identified mobile device or the secureelement to be securely stored in association with the mobile device.

The provisioning system may include: an encryption component forencrypting the received payment credentials, the encrypted paymentcredentials having a unique decryption key; and wherein communicating aderivation of the payment credentials communicates the unique decryptionkey.

In embodiments of the system, the provisioning system is a remotelyaccessible server of an issuing authority, a security gateway, ortrusted service manager, and wherein the communication module forcommunicating the payment credentials or a derivation of the paymentcredentials to the identified mobile device or the secure element uses asecure channel of communication.

In alternative embodiments, the provisioning system is a kiosk having aprocessor local to the receiving device, and wherein the kiosk includesthe communication module for establishing a communication channelbetween the kiosk and the mobile device for communicating the paymentcredentials or a derivation of the payment credentials. The kiosk mayact as an intermediary for a remotely accessible server and the systemincludes a server communication module for using the received identifierto identify and/or verify a user or account at the remotely accessibleserver.

The provisioning system may further includes: an authorization componentfor requesting authorization from a trusted service manager to access asecure element and receiving a security key to access the secureelement.

The provisioning system may further include: an additional credentialscomponent for communicating additional credentials to the identifiedmobile device or the secure element to be securely stored in associationwith the mobile device, wherein the additional credentials are requiredin use in addition to the payment credentials or derivation of thepayment credentials to carry out a transaction. In one embodiment, theadditional credentials may be card verification values. In anotherembodiment, the additional credentials may be in the form of a dynamicverification application or algorithm for generating dynamicverification values. The method may include obtaining the additionalcredentials from a remotely accessible server using the identifier andforwarding the additional credentials to the mobile device.

The identifying component for identifying a mobile device correspondingto the identifier may include functionality for determining whether ornot a mobile device or a secure element corresponding to the identifierhas been registered with a remotely accessible server and, if the mobiledevice has been registered, identifying a corresponding communicationaddress of the mobile device or secure element.

The communication module for communicating the payment credentials or aderivation of the payment credentials to the identified mobile device tobe securely stored in association with the mobile device, includesfunctionality for communicating the payment credentials or a derivationof the payment credentials to the mobile device to be stored in a secureelement, wherein the secure element is one of the group of: a secureelement provided in the mobile device, a secure element embedded in alayer which sits between a communication component of the mobile deviceand a communication component interface of the mobile device, a secureelement provided in a communication component of the mobile device, acloud-based secure element associated with the mobile device.

In further embodiments, the system may include: a point of sales devicecomprising: a payment credentials obtaining component for obtainingpayment credentials from a portable payment device presented by aconsumer at the receiving device; an identifier receiver for receivingan identifier entered by the consumer into the point of sales device; acommunication module for communicating the payment credentials andidentifier to a remotely accessible server for further communication ofthe payment credentials or a derivation of the payment credentials to amobile device to be securely stored in association with the mobiledevice.

In a further aspect of the present invention, a kiosk is provided toallow a user to provision a mobile device with credentials from theuser's credential storage instruments also referred to as portablepayment devices. The kiosk includes a credential storage instrumentreader to retrieve credentials from a credential storage instrument. Thekiosk also includes a mobile device interface to establish acommunication channel with a mobile device, and to load credentials fromthe credential storage instrument onto the mobile device via thecommunication channel.

According to a fourth aspect of the present invention there is provideda computer program product for provisioning payment credentials usableby a mobile device in conducting a payment, the computer program productcomprising a computer-readable medium having stored computer-readableprogram code for performing the steps of the first aspect of the presentinvention and one or more additionally defined features listed above.

According to a fifth aspect of the present invention there is provided acomputer program product for provisioning payment credentials usable bya mobile device in conducting a payment, the computer program productcomprising a computer-readable medium having stored computer-readableprogram code for performing the steps of the second aspect of thepresent invention and one or more additionally defined features listedabove.

Further features of the invention provide for the computer-readablemedium to be a non-transitory computer-readable medium and for thecomputer-readable program code to be executable by a processing circuit.

In order for the invention to be more fully understood, implementationsthereof will now be described with reference to the accompanyingdrawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of a first embodiment of a system inaccordance with the present invention;

FIG. 2 is a schematic diagram of showing variations to the firstembodiment FIG. 1;

FIG. 3 is a schematic diagram of showing variations to the firstembodiment FIG. 1;

FIG. 4A is a flow diagram of a method carried out at a provisioningsystem in accordance with the present invention;

FIG. 4B is a flow diagram of an embodiment of the method of FIG. 4A;

FIG. 5 is a flow diagram of a method carried out at a point of saledevice in accordance with the present invention;

FIG. 6A is a block diagram of an aspect of a system in accordance withthe present invention;

FIG. 6B is a block diagram of an aspect of a system in accordance withthe present invention;

FIG. 7 is a swim-lane flow diagram of an embodiment of a method inaccordance with the present invention;

FIG. 8 is a swim-lane flow diagram of another embodiment of a method inaccordance with the present invention;

FIG. 9A illustrates a second embodiment of a system in accordance withthe present invention;

FIG. 9B is a block diagram of a kiosk of the embodiment of the system ofFIG. 9A;

FIG. 9C is a schematic diagram of a system of the embodiment of FIG. 9A;

FIG. 9D is a flow diagram of a method of the embodiment of FIG. 9A;

FIG. 10 is a swim-lane flow diagram of the embodiment of FIG. 9A;

FIG. 11 illustrates a block diagram of a computing device in whichvarious aspects of the invention may be implemented; and

FIG. 12 illustrates a block diagram of a communication device that canbe used in various embodiments of the invention.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are setforth in order to provide a thorough understanding of the invention.However, it will be understood by those skilled in the art that thepresent invention may be practiced without these specific details. Inother instances, well-known methods, procedures, and components have notbeen described in detail so as not to obscure the present invention.

Methods and systems for provisioning payment credentials or derivationsof payment credentials usable by a mobile device in conducting acontactless payment are described.

Embodiments of the invention include a method carried out at a remotelyaccessible server for provisioning payment credentials or derivationsthereof to a mobile device via a receiving device at which a portablepayment device or credential storage instrument such as a payment cardmay be input. The receiving device may be, for example, a point-of-saledevice, an automated teller machine, or other intermediary device.

The payment credentials may be provisioned securely to the mobile devicefrom the remotely accessible server via channels to a secure elementassociated with the mobile device.

The payment credentials may be provisioned to the mobile device or,alternatively, the payment credentials may be stored at the remotelyaccessible server in an encrypted form and a unique decryption key maybe provisioned to the mobile device.

Other embodiments of the invention provide a kiosk to allow a user toprovision a mobile device with credentials from the user's credentialstorage instruments. By providing a kiosk as an interface between theuser's mobile device and the user's credential storage instruments,manual input of the credentials can be avoided because such credentialscan be read directly from the user's credential storage instruments.Furthermore, the kiosk can act as a communication intermediary betweenthe mobile device and entities involved in the provisioning process suchas an issuer or a trusted service manager to avoid wireless data usageon the mobile device during the provisioning process. Thus, embodimentsof the present invention provide a convenient and cost-effective way toenable mobile devices with digital wallet applications for use incontactless transactions.

These and additional embodiments are now described in detail.

FIG. 1 illustrates a block diagram of an exemplary system (100)according to embodiments of the invention. The system includes a mobiledevice (112) and a portable payment device (114) of a consumer (102).The system further includes a receiving device for the portable paymentdevice (114) and, in this embodiment, the receiving device is in theform of a point of sales device (120). The system further includes aremotely accessible server (140) which, in the exemplary system (100),is in communication with the point of sales device (120) via a paymentprocessing network (130). While the figure only shows one consumer(102), one mobile device (112), one portable payment device (114) andone point of sales device (120), it will be appreciated that this ispurely for illustrative purposes and that the invention anticipates oneor more of each.

The mobile device (112) may be any suitable mobile device having asecure element (113). The secure element (113) may be embedded in themobile device, disposed within a micro secure digital (SD) or similarcard form factor which is placed in a micro SD card slot of the mobiledevice (112).

Alternatively, the secure element (113) may be disposed within acommunication component of the mobile device, such as a universalintegrated circuit card (UICC). It is also anticipated that in someembodiments the secure element (113) may be disposed in an expansiondevice which may be connected to a mobile device or alternativelydisposed within, for example a label, tray or card which is then placedin between a UICC and a UICC interface of the mobile device such thatthe secure element can intercept and appropriately process anycommunication sent between the UICC and the mobile device andconsequently, between the mobile device and a mobile communicationnetwork.

It is further anticipated that the secure element (113) may be acloud-based secure element using host card emulation (HCE) which enablesnetwork-accessible storage external to the mobile device (112) with anapplication on the mobile device (112) configured to emulate the cardfunctions.

Exemplary mobile devices include smart phones, feature phones, tabletcomputers, personal digital assistants, or the like. The mobile device(112) is in data communication with the remotely accessible server over,for example a mobile data or mobile communication network, and is atleast configured to securely receive, store, release and transmitpayment credentials or derivations of payment credentials. For instance,the mobile device (112) may be any such device which meets anyappropriate financial or payment scheme standards, such as, for example,the Global Platform Card Specification. Embodiments of the inventionprovide for an appropriate mobile software application to be resident onthe mobile device (112) which allows a user thereof to interface withthe secure element (113) coupled thereto, or associated with it in acloud-based architecture, and which may also facilitate communicationsbetween the mobile device (112) and the secure element (113).

The software application may provide: a user interface to facilitate theentry of a passcode into the mobile device (112) to be compared to anoffset stored in the secure element (113); a list from which users canselect payment credentials to be used; notifications of receipt or useor payment credentials or the like. The user interface may include amenu from which at least some of these communications can be initiated.Embodiments of the invention further provide for such an interface to beprovided by a SIM Application Toolkit protocol (commonly referred to asthe STK protocol) implementation or the like.

The portable payment device (114) in the illustrated embodiment is asecurity integrated circuit bank card. Such cards are also known as‘chip and pin’ cards or ‘EMV smart cards’. The portable payment device(114) has payment credentials, which may be track 2 and/or track 2equivalent information (such as EMV tag 57 data), stored therein. Track2 and track 2 equivalent information may include a bank identificationnumber (BIN), a primary account number (PAN), an expiration date, aservice code, discretionary data such as card verification values (CVV)as well as any relevant spacing and redundancy checks. In addition tothis, embodiments of the invention provide for the portable paymentdevice (114) to contain payment credentials which may include any one ormore of a customer name and/or date of birth, a BIN, a PAN, a servicecode, an expiration date, CVV1 or CVV2 numbers, a PIN block or offset, abank account number, a branch code, a loyalty account number oridentifier, credit and/or debit card number information, account balanceinformation and/or other consumer information. In other embodiments ofthe invention, the payment credentials may include track 1 and/or track3 information.

The point of sales device (120) may be any suitable device configured toobtain payment credentials from appropriate portable payment devices andto communicate these payment credentials to a payment processing networkor financial institution network. The point of sales device (120) may beconfigured to obtain payment credentials from portable payment devicesvia any appropriate contact or contactless communications interfacewhich may, for example be ISO/IEC 7813, ISO/IEC 7816 or ISO/IEC 14443standards where applicable.

The point of sales device (120) may include one or more of various meansfor retrieving information from a portable payment device including theuser placing the portable payment device (114) in physical contact withthe point of sales device (120), for example, by swiping or inserting amagnetic stripe card into a magnetic stripe reader, or by inserting achip-card into a chip-card reader slot, or the user placing the portablepayment device (114) in close proximity with the point of sales device(120), for example, by placing a contactless card in close proximity toa contactless card reader, or by placing a printed medium, for example,with a bar code or quick response (QR) code in front of an infraredscanner.

In the illustrated exemplary system (100), the point of sales device(120) is a handheld point of sales device. In addition to this, thepoint of sales device (120) is configured to receive an identifierentered by a consumer via, for example, a keypad of the point of salesdevice (120).

The point of sales device (120) is further configured to format thepayment credentials as well as the identifier into a financialtransaction message and to communicate this message to the paymentprocessing network (130). The financial transaction message may, forexample, be an ISO 8583 message. Furthermore, the point of sales device(120) is configured to insert a server routing code into the financialtransaction message such that the financial transaction message isrouted to the remotely accessible server (140) by the payment processingnetwork (130) using the server routing code. The server routing code maybe placed in the ‘BIN’ field of the financial transaction message.

The payment processing network (130) is a network of financialinstitutions and payment processing institutions and is configured toroute financial transaction messages between, for example, merchants,acquirers, and issuers, amongst others. An example of such a paymentprocessing network is VisaNet™ having a plurality of acquiring andissuing financial institutions being a part of the network.

The remotely accessible server (140) may be any appropriate severcomputer or distributed server computer system and has a database (142)stored in a digital memory therein and also has a secure memory which,in a preferred embodiment is within a hardware security module (144) ofthe remotely accessible server. The remotely accessible server (140) isconfigured to receive payment credentials from a point of sales device(e.g. 120), where the payment credentials have been obtained from aportable payment device (e.g. 114) presented by a consumer (e.g. 102) atthe point of sales device (120).

The remotely accessible server may be configured to encrypt the paymentcredentials, the encrypted payment credentials having a uniquedecryption key. The encryption may be performed in the hardware securitymodule (144). In one embodiment, the key to decrypt the paymentcredentials is kept by the remotely accessible server (140) and theencrypted payment credentials are sent to the mobile device (112) forstorage in the secure element (114) associated with the mobile device(112). In another embodiment, the encrypted payment credentials arestored in the hardware security module (144) of the remotely accessibleserver (140) and the decryption key is sent to the mobile device (112)for storage in the secure element (113) associated with the mobiledevice (112).

In addition to this, the remotely accessible server (140) is configuredto receive an identifier from the point of sales device (120) which isentered by the consumer (102) into the point of sales device (120). Theremotely accessible server (140) is configured to then identify a mobiledevice (e.g. 112), or a secure element (113) associated with a mobiledevice (112), corresponding to the identifier and to communicate thepayment credentials to the mobile device (112) to be stored in a secureelement (113) associated with the mobile device (112).

This may be performed by using the identifier to query the database(142) so as to obtain a communication address of the mobile device (112)associated with the identifier. The payment credentials can then be sentto the mobile device (112) using the communication address. Theidentifier received by the remotely accessible server may be, forexample, any one or more of a mobile station international subscriberdirectory number (MSISDN), an email address, a social networkidentifier, a predefined consumer name, a consumer account number or thelike. The communication address of the mobile device may similarly be,for example, any one or more of an MSISDN, an email address, a socialnetwork identifier, a predefined consumer name, a consumer accountnumber or the like. The identifier and communication address may be thesame.

Embodiments of the invention provide for the remotely accessible serverto be configured to associate one or more of the group of: theidentifier; decryption key; encrypted payment credentials; andcommunication address with a user profile in the database.

In some embodiments of the invention the role played by the remotelyaccessible server (140) may be similar to that of a trusted servicemanager (TSM) and accordingly may meet any security or data integrityrequirements imposed by relevant financial or payment scheme standards,such as, for example, the Global Platform Card Specification.

In use, a consumer (102) may wish to provision his or her paymentcredentials or a derivation thereof to a secure element (113) on his orher mobile device (112) such that the mobile device (112) may be used toconduct contactless payments at either brick-and-mortar merchants oronline merchants.

To do this, the consumer, having already registered his or her mobiledevice (112) with the remotely accessible server (140) and associated itwith an identifier and communication address, visits, for example, abrick-and-mortar merchant and presents the merchant with his or herportable payment device (114). The portable payment device (114) isinterfaced with a point of sales device (120) of the merchant and a‘credential transfer’ menu option, for example is selected on the pointof sales device (120). The consumer (102) may be prompted to enter a PINwhich he or she enters into the point of sales device (120), followingwhich, the consumer (102) may be prompted to enter his or heridentifier. The consumer (102) enters their predetermined identifier,which has been registered with the remotely accessible server (140),into the point of sales device (120).

Having received the consumer's PIN, the point of sales device (120) isable to extract payment credentials from the portable payment device(114). The point of sales device (120) formats the payment credentialsinto a financial transaction message. The point of sales device (120)may also include the identifier in the financial transaction message aswell as a server routing code. The server routing code may be similar toa BIN and ensures that the financial transaction message is routed tothe remotely accessible server (140) by the payment processing network(130)

The financial transaction message is received at the remotely accessibleserver (140). The remotely accessible server uses the identifiercontained in the financial transaction message to identify acommunication address of an associated mobile device (112). The remotelyaccessible server (140) uses the communication address to communicatethe payment credentials or a derivation of the payment credentials tothe mobile device (112) for storage in the secure element (113)associated therewith.

The payment credentials are then received by the mobile device (112) andstored securely in the secure element (113) of the mobile device (112).The user may be prompted for a PIN before the payment credentials arestored in the secure element. In some embodiments the paymentcredentials are provisioned to the mobile device (112) from the remotelyaccessible server (140) and stored in the secure element (113) viaover-the-air (OTA) provisioning. This accordingly may enable the user tomake contactless payments using his or her mobile device (112) as acontactless portable payment device, where the credentials provided bythe mobile device (112) to the merchant's appropriately configured pointof sales device are those of the user's portable payment device (114).

In some embodiments, the remotely accessible server (140) may encryptthe payment credentials and a unique decryption key may be associatedwith the payment credentials. One of either the encrypted paymentcredentials or the decryption key may then be stored in secure memory,such as a hardware security module (144) of the remotely accessibleserver. The other of the encrypted payment credentials or the decryptionkey may be sent to the secure element (113) associated with the mobiledevice (112). The payment credentials may be encrypted using anyappropriate encryption algorithm such that, once encrypted, the paymentcredentials may only be decrypted using the unique decryption key. Ifthe decryption key is sent to the mobile device (112) for storage in thesecure element (113), this decryption key is not stored at the remotelyaccessible server nor in its hardware security module.

The encrypted payment credentials or decryption key received by themobile device (112) are stored securely in the secure element (113) ofthe mobile device (112). The user may be prompted for a PIN before theencrypted payment credentials or decryption keys are stored in thesecure element. In some embodiments decryption keys are provisioned tothe mobile device (112) from the remotely accessible server (140) andstored in the secure element (113) via over-the-air (OTA) provisioning.

In the scenario of the derivation of the payment credentials in the formof a decryption key is stored at the secure element (113) associatedwith the mobile device (112), a user may present the identifier to amerchant as a payment method in conducting a transaction. The merchantcan request payment credentials from the remotely accessible server(140) and, in conjunction, communicate the identifier to the remotelyaccessible server (140). The remotely accessible server (140) can usethe received identifier to identify a mobile device (112) and request adecryption key from the identified mobile device (112). The mobiledevice (112), upon receiving this request, may then prompt the user fora PIN, passcode or password before communicating a relevant decryptionkey to the remotely accessible server (140) so that correspondingencrypted payment credentials can be decrypted and communicated to themerchant and/or the merchant's acquirer, and/or the payment processingnetwork so that the transaction may be completed.

FIG. 2 illustrates an exemplary system (200) according to a secondembodiment of the invention. The system is similar to that which isillustrated in FIG. 1 and like reference numerals refer to like systems,entities or devices. The system (200) of FIG. 2 differs from that ofFIG. 1 in that the point of sales device in this embodiment is anautomatic teller machine (ATM) (222). The ATM (222) may be any suitableATM and is configured to obtain payment credentials from a portablepayment device (214) of a consumer (202) and to communicate thesepayment credentials to a payment processing network (230) or financialinstitution network. The ATM (222) may be configured to obtain paymentcredentials from the portable payment device (214) via any appropriatecontact or contactless communications interface, for example a cardreader or near field communication (NFC) interface.

The ATM (222) in the illustrated embodiment is configured to receive anidentifier entered by a consumer (202) via, for example, a keypad of theATM (222). The ATM (222) is further configured to format the paymentcredentials as well as the identifier into a financial transactionmessage and to communicate this message to the payment processingnetwork (230). The financial transaction message may, for example, be anISO 8583 message. Furthermore, the ATM (222) is configured to insert aserver routing code into the financial transaction message such that thefinancial transaction message is routed to the remotely accessibleserver (240) by the payment processing network (230) using the serverrouting code. The server routing code may be placed in the ‘BIN’ fieldof the financial transaction message.

Once the payment credentials are received at the remotely accessibleserver, they may communicated or a derivation of the payment credentialsmay be communicated to the mobile device for storage in a secure elementthereof as has been described in the foregoing description.

The system (200) may be put to use by a user (202) in a similar mannerto that system of FIG. 1. The user (202) presents his or her portablepayment device (214) to a portable payment device interface of the ATM(222). The user may be prompted for a PIN, responsive to a correct entryof which, the user (202) user selects a ‘credential transfer’ optionfrom a menu displayed on a screen of the ATM (222). The user (202) willalso be prompted for an identifier, which he or she enters into the ATM(222) via keypad of the ATM (222). The ATM (222) obtains paymentcredentials from the portable payment device (214) and formats thepayment credentials, identifier, as well as the server routing code intoa financial transaction message which is then sent to the paymentprocessing network (230) and routed from there to the remotelyaccessible server (240). Similar to the in-use scenario of FIG. 1, thepayment credentials are then communicated to the user's mobile device(926) to be stored in a secure element thereof.

FIG. 3 illustrates yet another exemplary system (300) according to athird embodiment of the invention. The system (300) is similar to thatwhich is illustrated in FIGS. 1 and 2, and like reference numerals referto like systems, entities or devices. The system (300) of FIG. 3 differsfrom that of FIGS. 1 and 2 in that the mobile device (316) does not havean embedded secure element. Rather, the mobile device (316) has acryptographic expansion label (318) in which a secure element isdisposed. The cryptographic expansion label (318) has electricalcontacts disposed on a top side and a bottom side thereof whichinterface to a communication component (317) and a communicationcomponent interface of the mobile device (316) respectively. Thecryptographic expansion label (318) may then be attached to thecommunication component (317) which is inserted into a communication bayof the mobile device (316) such that the secure element can interceptand appropriately process any communication sent between thecommunication component (317) and the mobile device (316) andconsequently, between the mobile device (316) and a mobile communicationnetwork. In the illustrated embodiment, the communication component is auniversal integrated circuit card (UICC).

FIG. 4A illustrates a flow diagram of a method according to oneembodiment of an aspect of the invention. The method is conducted at aprovisioning system which may be a remotely accessible server, similarto those described in the foregoing description with reference to FIGS.1 to 3, or a dedicated kiosk as described further below in relation toFIGS. 9A to 9D.

The method includes a series of steps, a first (402) of which is thestep of receiving payment credentials from a receiving device which maybe a point of sales device, incorporated into or used in associationwith a point of sales device, as described with reference to FIGS. 1 to3, or a credential storage instrument reader of a kiosk with referenceto FIGS. 9A to 9D, or another form of receiving device for receivingpayment credentials. The point of sales device may, for example, be anautomatic teller machine, a merchant point of sales terminal or apersonal PIN entry device (PPED).

The payment credentials received from the point of sales device areobtained from a portable payment device (also referred to below inrelation to the embodiment of FIGS. 9A to 9D as a credential storageinstrument) which is presented by a consumer at the receiving device.The portable payment device may be a credit or debit card which may beany one of a magnetic stripe bank card, a security integrated circuitbank card or a contactless bank card. The payment credentials may betrack 1 data, track 2 data, track 3 data or track 2 equivalent data(such as EMV tag 57 data). Furthermore, the payment credentials mayinclude an account holder name and/or date of birth, a bankidentification number (BIN), a primary account number (PAN), a servicecode, an expiration date, card verification values (CVV1 or CVV2), a PINblock or offset, a bank account number, a branch code, a loyalty accountnumber or identifier, credit and/or debit card number information,account balance information, and/or consumer information such as name,date of birth. The payment credentials may be received by the remotelyaccessible server via a payment processing network.

The method includes a step (404) of receiving an identifier from thereceiving device, for example, the point of sales device, or kiosk userinput interface. The identifier may be any one or more of a mobilestation international subscriber directory number (MSISDN), an emailaddress, a social network identifier, a predefined consumer name or aconsumer account number. In a preferred embodiment of the invention, thepayment credentials and identifier are received at the remotelyaccessible server in a financial transaction message, which may, forexample, be an ISO8583 message. Furthermore, the financial transactionmessage may be communicated from the point of sales device to theremotely accessible server via a payment processing network. Thefinancial transaction message may accordingly include a server routingcode such that the payment processing network is able to route thefinancial transaction message to the remotely accessible server.

The method includes a next step (406) of identifying a mobile deviceand/or a secure element of a mobile device corresponding to theidentifier. This step may include the step of determining whether or nota mobile device and/or secure element corresponding to the identifierhas been registered with the remotely accessible server and, if a mobiledevice and/or secure element has been registered, identifying acorresponding communication address of the mobile device and/or secureelement. This may be performed by using the identifier to query adatabase of the remotely accessible server so as to obtain thecommunication address of the mobile device and/or secure elementassociated with the identifier.

As an optional additional step (408), a registration or activationrequest may be sent to a trusted management service (TSM) which managessecurity keys or tokens that are used to access a secure element. Therequest may include the identifier. The TSM may authorize the unlockingof a secure element associated with the mobile device. The TSM may beprovided at the remotely accessible server or by a remote serviceprovided on a separate remotely accessible server.

The method includes a step (410) of communicating the paymentcredentials to the mobile device to be stored in a secure elementassociated with the mobile device. This may include communicating thepayment credentials to the mobile device using the communicationaddress. This may also include communicating the payment credentials tothe secure element associated with the mobile device using anidentification code of a secure element in order to set up a securechannel of communication with the secure element which may be via themobile device. In some embodiments as described further in relation toFIG. 4B, a derivation of the payment credentials is communicated to themobile device or secure element, for example, the derivation of thepayment credentials may be a decryption key corresponding to remotelystored encrypted payment credentials.

As a further optional additional step (412), additional credentials maybe requested by or supplied by the remotely accessible server. Theadditional credentials may be credentials which cannot be automaticallyread from a portable payment device such as a printed card verificationvalue (for example the CVV2 number) which is human-readable from theportable payment device. In this case, the additional credentials may berequested by the remotely accessible server and obtained from theconsumer via the point of sales device.

The additional credentials may also include dynamic card verificationvalue (dCVV) software that is used to generate a dCVV for individualtransactions. Such additional credentials may be identified using theidentifier and supplied by the remotely accessible server or by aseparate remotely accessible server during the provisioning process. Theadditional credentials may be communicated to the secure elementassociated with the mobile device. These may be communicated separatelyto the payment credentials or derivation of the payment credentials.

The secure element of the mobile device may, according to someembodiments of the invention, be embedded in a label, card or tray asdescribed previously in the forgoing description. Before communicatingthe payment credentials to the mobile device, the remotely accessibleserver may encrypt the payment credentials using any one of a number ofencryption algorithms. Exemplary encryption algorithms include AdvanceEncryption Standard (AES), Data Encryption Standard (DES), Triple DataEncryption Standard/Algorithm (TDES/TDEA), Secure Socket Layer (SSL),Blowfish, Serpent, Twofish, International Data Encryption Algorithm(IDEA), Rivest, Shamir, & Adleman (RSA), Digital Signature Algorithm(DSA), Tiny Encryption Algorithm (TEA), extended TEA (XTEA), and/orother encryption algorithms or protocols. In some embodiments, thedecryption key, also referred to as the private key, is stored in asecure memory of the remotely accessible server in association with theidentifier, such that only the remotely accessible server, or a hardwaresecurity module thereof, may decrypt the payment credentials beforepresentment to, for example, a merchant. In this embodiment, the paymentcredentials are stored in their encrypted form in the secure element ofthe mobile device.

FIG. 4B illustrates a flow diagram of a method according to anotherembodiment of an aspect of the invention. The method is conducted atremotely accessible server, such as that of FIGS. 1 to 3. The methodincludes a series of steps, a first (422) of which is receiving paymentcredentials from a receiving device such as point of sales devicesimilar to that of step (402) of FIG. 4A.

The method includes a next step (424) of receiving an identifier fromthe receiving device such as a point of sales device similar to that ofstep (404) of FIG. 4A.

The method includes a following step (426) of encrypting the paymentcredentials. The payment credentials may be encrypted with anyappropriate algorithm and once encrypted, have a unique decryption key.Exemplary encryption algorithms include, but are not limited to, AdvanceEncryption Standard (AES), Data Encryption Standard (DES), Triple DataEncryption Standard/Algorithm (TDES/TDEA), Secure Socket Layer (SSL),Blowfish, Serpent, Twofish, International Data Encryption Algorithm(IDEA), Rivest, Shamir, & Adleman (RSA), Digital Signature Algorithm(DSA), Tiny Encryption Algorithm (TEA), extended TEA (XTEA), and/orother encryption algorithms or protocols.

As the decryption key is unique to those payment credentials, only thatdecryption key may be used to decrypt those payment credentials. Theunique decryption key, which in some embodiments may be a private key,is not stored in the same location as the encrypted payment credentials.

The method includes a next step (428) of storing one of either theencrypted payment credentials or the decryption key in a secure memoryof the remotely accessible server, which in a preferred embodiment, is ahardware security module. The encrypted payment credentials or theunique decryption key, communication address, and identifier may beassociated with a user profile stored in a database of the remotelyaccessible server. Upon receiving, for example, a unique decryption key,the corresponding payment credentials, stored in the hardware securitymodule, may be identified.

The method includes a following step (430) of identifying a mobiledevice and/or a secure element corresponding to the identifier. Thisstep is similar to step (406) of FIG. 4A.

The method includes a final step (432) of communicating the other of theencrypted payment credentials and the unique decryption key to themobile device to be stored in a secure element associated with themobile device. This may include communicating to the mobile device usingthe communication address. The secure element of the mobile device may,according to some embodiments of the invention, be embedded in a label,card or tray as described previously in the forgoing description.

As only one of the encrypted payment credentials and the decryption keyis only stored in the secure element of the mobile device, the encryptedpayment credentials cannot be decrypted, and consequently cannot beused.

In the scenario where the encrypted payment credentials are stored atthe remotely accessible server and the unique decryption key istransmitted to the secure element of the mobile device, the uniquedecryption key is purged and not stored at the hardware security moduleof the remotely accessible server.

This scenario, which may be considered an inverse of one where thepayment credentials are stored in the secure element of the mobiledevice, is advantageous in that if the secure element of the mobiledevice is compromised, only the decryption keys of encrypted paymentcredentials can be obtained. Furthermore, in the event that the secureelement is compromised, the decryption keys stored therein can simply berevoked, without payment credentials having to be re-issued.

FIG. 5 illustrates a flow diagram of a method according to anotheraspect of the invention. The method is conducted at a suitably modifiedpoint of sales device, such as any of those described in the foregoingdescription with reference to FIGS. 1 to 3.

The method includes a first step (502) of obtaining payment credentialsfrom a portable payment device presented by a consumer at the point ofsales device. This may be performed in a manner similar to conventionalpayment credential access operations, such as for example via an ISO7816, or ISO/IEC 14443 communication protocol or the like. The paymentcredentials obtained might be considered as ‘card present’ paymentcredentials in that they provide sufficient information for a subsequenttransaction using the payment credentials to be considered a cardpresent transaction. The payment credentials may then, for instance, betrack 1 data, track 2 data, track 3 data or track 2 equivalent data(such as EMV tag 57 data). Furthermore, the payment credentials mayinclude an account holder name and/or date of birth, a bankidentification number (BIN), a primary account number (PAN), a servicecode, an expiration date, card verification values (CVV1 or CVV2), a PINblock or offset, a bank account number, a branch code, a loyalty accountnumber or identifier, credit and/or debit card number information,account balance information, or consumer information such as name, dateof birth.

The method includes a next step (504) of receiving an identifier enteredby the consumer into the point of sales device. The identifier may beany one or more of a one or more of a mobile station internationalsubscriber directory number (MSISDN), an email address, a social networkidentifier, a predefined consumer name or a consumer account number.

The method further includes a next step (506) of communicating thepayment credentials and identifier to a remotely accessible server forfurther communication to a secure element associated with a mobiledevice of the consumer. This step may include formatting the paymentcredentials and identifier into a financial transaction message. Thefinancial transaction message may, for example, be an ISO8583 financialtransaction message. The point of sales device may further be configuredto insert a server routing code into the financial transaction messagesuch that the financial transaction message is routed to the remotelyaccessible server by a payment processing network and not, for examplean issuing bank as indicated by the BIN originally included in thepayment credentials.

If requested, additional credentials may be input by the consumer at thepoint of sales device and communicated to the remotely accessibleserver, for example, non-machine readable card verification values (forexample, CVV2 data).

A remotely accessible server for provisioning of payment credentials,such as that of FIGS. 1, 2 and 3, is illustrated in FIG. 6A. Theremotely accessible server (140) has a payment credentials receiver(602) for receiving payment credentials. The payment credentials may bereceived from a point of sales device whereat the payment credentialsmay have been obtained from a portable payment device presented by aconsumer. The remotely accessible server (140) has an identifierreceiver (604) for receiving, from the point of sales device, anidentifier entered by the consumer. In some embodiments the paymentcredentials receiver (602) and the identifier receiver (604) may beprovided in a single receiver which may be configured to receive paymentcredentials and an identifier in a financial transaction message. Insome embodiments, the financial transaction message may be an ISO 8583message.

The remotely accessible server (140) may include an encryption component(606) for encrypting the received payment credentials, the encryptedpayment credentials having a unique decryption key. The remotelyaccessible server (140) may have a secure memory (608) incorporatedtherein or associated with the remotely accessible server (140) forstoring one of the encrypted payment credentials or the uniquedecryption key. In the illustrated embodiment, the secure memory (608)and the encryption component (606) are within a hardware security module(644) of the remotely accessible server (140).

The remotely accessible server (140) may include an identifyingcomponent (610) for identifying a mobile device and/or secure elementcorresponding to the identifier. In the illustrated embodiment, theidentifying component (610) forms part of a database (642) of theremotely accessible server (140) in which one or more of the group of:an identifier; decryption key; encrypted payment credentials; andcommunication address may be associated with a user profile.

The remotely accessible server (140) further includes a communicationmodule (612) for communicating to the identified mobile device or thesecure element associated with the mobile device. The communicationmodule may communicate with the mobile device via any appropriate mobilecommunication or mobile data network. The communication module (612) mayset up a secure communication channel with the secure element via themobile device for communication of one of the encrypted paymentcredentials or the unique decryption key.

The remotely accessible server (140) may optionally include anauthorization component (646) for sending a registration or activationrequest to a trusted management service (TSM) which manages securitykeys or tokens that are used to access a secure element.

The remotely accessible server (140) may optionally include anadditional credentials component (648) for requesting or supplyingadditional credentials for communicating to the mobile device or thesecure element. The additional credentials component (648) may requestadditional credentials from a consumer via a point of sale device, forexample, human-readable card verification values, which are forwardedfor storage on the secure element associated with the mobile device.Alternatively or additionally, the additional credential component (648)may supply additional credentials stored at the remotely accessibleserver or a related remote server, for example, in the form of dynamiccard verification value (dCVV) software used to generate a dCVV forindividual transactions. The supplied additional credentials may beforwarded for storage on the secure element associated with the mobiledevice.

A point of sales device for provisioning of payment credentials, such asthat of FIGS. 1, 2 and 3, is illustrated in FIG. 6B.

The point of sales device (120) may include a payment credentialsobtaining component (652) which may be in the form of a card reader orscanner as previously described. The point of sales device (120) mayalso include an identifier receiver (654) for receiving an identifier asinput by a consumer.

The point of sales device (120) may include a communication module (656)for communication with a remotely accessible server. The communicationmodule (656) may communicate with the remotely accessible serversecurely using financial transaction messages.

In some embodiments, the point of sales device (120) may include anauthorization component (658) for sending a registration or activationrequest to a trusted management service (TSM) which manages securitykeys or tokens that are used to access a secure element.

In further embodiments, the point of sales device (120) may include anadditional credentials receiver (659) for receiving additionalcredentials from a consumer, for example, in the form of a printed cardverification value which is not obtainable by the payment credentialsobtaining component (652).

FIG. 7 shows a swim-lane flow diagram illustrating the flow between amobile device (112), a point of sales device (120), and a remotelyaccessible server (140) according to embodiments. The remotelyaccessible server (140) may be provided by a financial institution orservice provider. In one embodiment, the remotely accessible server(140) is part of a payment processing network.

A consumer may present (701) his portable payment device (for example, apayment card) at the point of sales device which may extract paymentcredentials from the portable payment device. The consumer may alsoprovide (702) an identifier. For example, the consumer may present amerchant with his payment card which may be inserted into a point ofsales device and a “credential transfer” transaction may be requested.The consumer may be prompted for his payment card PIN which may beentered into the point of sales device via a keypad. The point of salesdevice may also prompt the consumer for an “alias” which is used as anidentifier for the consumer and his mobile device.

The point of sales device may format (703) the extracted paymentcredentials and the identifier into a transaction message, for example,an ISO8583 message. This message is similar to a normal point of saletransaction message with the addition of the provided identifier. TheBIN field may be populated with a payment processing network BIN so thatthe message is routed to a payment processing gateway instead of anissuer. The consumer's BIN remains provided in the message.

The remotely accessible server receives (704) the transaction messageand extracts the payment credentials and the identifier. The identifieris used to identify (705) one or more of: a consumer having a registeredmobile device and/or secure element; an account having a registeredmobile device and/or secure element; or the mobile device and/or secureelement itself.

The remotely accessible server may encrypt (706) the payment credentialsand a unique decryption key may be generated specific to the paymentcredentials. One of the encrypted payment credentials and the uniquedecryption key may be securely communicated (707) to the secure elementassociated with the mobile device, whilst the other of the encryptedpayment credentials and the unique decryption key may be stored (708) atthe remotely accessible server.

The secure element associated with the mobile device may receive (709)either the encrypted payment credentials or the unique decryption keyand may prompt the user for a PIN (710), the offset of which is storedin association with the payment credentials or the decryption key suchthat the payment credentials will only be released by the secure elementin the event that the correct PIN is entered.

FIG. 8 is a swim-lane flow diagram illustrating the flow between amobile device (112), a point of sales device (120), and a remotelyaccessible server (140) according to an embodiment of the describedmethod in which the decryption key for the payment credentials isprovisioned to the secure element associated with the mobile device.

A consumer may present (801) an identifier to a merchant as a paymentmethod in conducting a transaction. The merchant may request (802)payment credentials from the remotely accessible server sending theidentifier with the request.

The remotely accessible server may use the received identifier toidentify (803) a mobile device associated with a secure element at whicha decryption key is stored. The remotely accessible server may request(804) the decryption key via a secure communication with the secureelement which may be via the mobile device.

The mobile device upon receiving the request may prompt (805) theconsumer for a PIN before communicating (806) the decryption key to theremotely accessible server.

The remotely accessible server may retrieve (807) the encrypted paymentcredentials from its storage and decrypt (808) the payment credentialsusing the decryption key. The payment credentials may then betransmitted (809) and received (810) at a point of sales device oranother intermediary using a secure channel in order to complete thetransaction.

An advantage of storing payment credentials, encrypted, at a remotelyaccessible server instead of in a secure element of a mobile device,according to embodiments of the present invention, is that if the secureelement of the mobile device is compromised by a malicious third partyand information stored therein is obtained by that third party, theinformation obtained by the third party will not include paymentcredentials. This is in contrast to scenarios in which paymentcredentials are stored in the secure element and where the third partymay obtain and fraudulently make use of these payment credentials.

In addition to this, in the event that the secure element is compromisedor lost, the decryption keys stored therein can simply be revoked,without payment credentials having to be re-issued.

A further advantage of storing the payment credentials, encrypted, atthe remotely accessible server instead of in a secure element of amobile device is that the mobile device need not meet security standardsimposed by relevant standards or compliance authorities. For example,the secure element need not be EMV compliant or may not have to meet PCIDSS requirements.

Similarly as the unique decryption key is stored only in the secureelement of the consumer's mobile device, the corresponding encryptedpayment credentials cannot be decrypted, and consequently cannot beused, without the decryption key being released from the secure elementin which it is securely stored. Thus the consumer has ultimate controlover when his or her payment credentials may be used. Furthermore, ifthe remotely accessible server is compromised by a malicious thirdparty, encrypted payment credentials stored therein will be of no use tothat third party without a corresponding unique decryption key.

FIGS. 9A to 9D are now described which illustrate an alternativeembodiment of the invention in which the provisioning system is providedby a kiosk (901).

FIG. 9A illustrates a kiosk (901) which can be set up in retailerstores, shopping malls, airports, and other public places. For example,kiosk (901) can be conveniently set up at a mobile device retailer or amobile network operator store to allow users to provision their newlypurchased mobile device with digital wallet capabilities. In someembodiments, kiosk (901) can be bolted down to the floor or to a wallwith tamperproof hardware. Kiosk (901) can also be implemented to besmall, light, and compact enough to be portable such that kiosk (901)can easily be moved from location to location. For example, in someembodiments, kiosk (901) can be implemented in a form factor similar toa tablet computer or a laptop.

Kiosk (901) includes a display (902), a mobile device interface (910),and a credential storage instrument reader (920). Display (902) can besurrounded by a housing. Display (902) can be placed at a suitableheight (e.g., on a stand) to allow a user to easily read or seeinformation or images provided on display (902). Display (902) can beused to provide instructions to the user during the digital walletprovisioning process. Display (902) can also be used to showadvertisements, videos, and/or other images when kiosk (901) is notbeing used. Display (902) can also act as a user input interface such astouch screen display to accept user inputs.

Mobile device interface (910) is used to establish a communicationchannel or link between kiosk (901) and a mobile device. A mobile devicecan be a mobile phone, a personal digital assistant, a tablet computingdevice, portable media player device, or other suitable portablecomputing device that can store and run a digital wallet application.Mobile device interface (910) can be a physical connector as shown thatcan plug into a physical communication port of a mobile device. Forexample, the physical connector can be a USB connector that can pluginto a USB port (e.g., mini-USB) of a mobile device. The physicalconnector can also be a proprietary connector that is compatible with aproprietary communication port of some mobile device manufacturers. Thephysical connector can be provided as a plug, as part of a cable (e.g.,a retractable cable, an external cable, etc.) that can extend from thehousing of kiosk (901), or as part of a docking station or a cradlebuilt into the housing of kiosk (901). In some embodiments, kiosk (901)can include multiple types of connectors such that kiosk (901) can becompatible with a number of mobile device manufacturers. In someembodiments, mobile device interface (910) can be a wireless interface(e.g., wireless transceiver) that is used to establish an ad hoccommunication channel with a mobile device using NFC, RF, Bluetooth,Wi-Fi, or other wireless communication protocols during the digitalwallet provisioning process. Kiosk (901) may also include one or morephysical connectors in combination with one or more wireless interfacesthat can be used to establish a communication channel with a mobiledevice.

Credential storage instrument reader (920) of kiosk (901) is used toread or access a credential storage instrument (905) (also referred toherein as a portable payment device) to obtain credentials and/or otheruser or account information stored on credential storage instrument(905). Credential storage instrument reader (920) can be a magneticstripe reader or a chip-card reader to read credentials from credentialstorage instrument (905) via physical contact with credential storageinstrument (905). Credential storage instrument reader (920) can be aninfrared scanner such as a bar code or OR code scanner to readcredentials that are encoded as an image, or can be a contactless cardreader capable of communicating with credential storage instrument (905)via NFC, RF, Bluetooth, Wi-Fi, or other wireless communication protocolsto read credentials from credential storage instrument (905) in acontactless manner when credential storage instrument (905) is in closeproximity to kiosk (901). In some embodiments, kiosk (901) may includeone or more types of credential storage instrument reader describedabove.

Credential storage instrument (905) can be in the form of a card (e.g.,credit/debit or other payment card, identification card, driver'slicense card, transit card, access card, insurance card, retailerloyalty card, gift card, etc.) or other suitable structure. Credentialstorage instrument (905) can include a magnetic stripe and/or a memorychip for storing the user's credentials. Credential storage instrument(905) can also be a printed medium that includes an image encoding theuser's credentials such as a bar code or a QR code. In some embodiments,credential storage instrument (905) can also be a user's existing mobiledevice that has the user's credentials stored therein.

Credentials may include information stored on a credential storageinstrument that can be used to conduct a transaction with the credentialstorage instrument. For example, credentials can be information that isused to identify and/or verify the user, or to identify or access anaccount associated with the credential storage instrument. Credentialsmay include financial information, identification information, accountinformation, transit information (e.g., as in a subway or train pass),access information (e.g., as in access badges), etc. Some examples ofcredentials include bank account information, primary account number(PAN), bank identification number (BIN), credit or debit card number,expiration date, name, username, date of birth, driver's license number,address, social security number, passport number, insurance policynumber such as medical or auto insurance account number, retailer ortravel loyalty program account number, gift card number, transit fareaccount number, employee identification number, or the like. Credentialsmay also include additional information that is used to facilitate atransaction. For example, credentials may include a card verificationvalue (CVV) and/or a service code used to facilitate processing of atransaction.

In some embodiments, credentials may also include additional informationthat are used to facilities a transaction, but are not stored oncredential storage instrument (905) or cannot be retrieved by credentialstorage instrument reader (920) of kiosk (901). For example, credentialsmay include a card verification value 2 (CVV2) that is printed on theface of a credit card, but may not be retrieved by reading the magneticstripe of the card. Credentials may also include dynamically cardverification code (dCVV) software that is used to generate a dCVV forindividual transactions. For such credentials that are not stored oncredential storage instrument (905) or cannot be retrieved by credentialstorage instrument reader (920), kiosk (901) can obtain such credentialsfrom the issuer of credential storage instrument (905) during theprovisioning process such that these credentials can be loaded onto themobile device.

Credentials can be stored in a memory chip of credential storageinstrument (905) or can be encoded as an image printed on credentialstorage instrument (905). Credentials stored in credential storageinstrument (905) may also be stored in the form of magnetic data trackssuch as those traditionally associated with credits cards. Such tracksmay include Track 1 and Track 2. Track 1 (“International Air TransportAssociation”) stores more information than Track 2, and contains thecardholder's name as well as account number and other discretionarydata. This track is sometimes used by the airlines when securingreservations with a credit card. Track 2 (“American BankingAssociation”) is currently most commonly used. This is the track that isread by ATMs and credit card checkers. The ABA (American BankingAssociation) designed the specifications of this track and all worldbanks abide by it. It contains the cardholder's account, encrypted PIN,plus other discretionary data.

FIG. 9B illustrates a block diagram of a kiosk (901) according tovarious embodiments. Kiosk (901) includes one or more processors (921)coupled to a storage medium (204). Storage medium (204) stores machinereadable code that can be executed by processor (921) to provision amobile device with digital wallet capabilities. Kiosk (901) includes oneor more mobile device interface (910) and one or more credential storageinstrument reader (920). Kiosk (901) further includes display (925) andsound system (924) that can be used to provide a user with visual andaudio instructions during the digital wallet provisioning process. Whenkiosk (901) is not being used to provision a mobile device, display(925) and sound system 208 can be used to present other media such asadvertisements or informational videos and sounds. Kiosk (901) alsoincludes user input interface (926) to receive user inputs. User inputinterface (926) can be implemented with one or more of a touch screen, akeypad, a keyboard, a touch pad, a mouse, a track pad, a microphone, orother suitable user input interface components.

In some embodiments, kiosk (901) may include a network interface (923)to allow kiosk (901) to communicate, if necessary, with entities thatmay be involved with the digital wallet provisioning process. Forexample, network interface (923) may be used by kiosk (901) tocommunicate with an issuer of the credential storage instrument (e.g., abank that issued a credit card, a transit agency that issued a transitaccess card, a government agency that issued an identification card, aretailer that issued a loyalty program card, etc.). Network interface(923) may also be used by kiosk (901) to communicate with a trustedservice manager to acquire security keys or tokens that are used toprovision a mobile device with digital wallet capabilities. Kiosk (901)may also communicate with a mobile network operator via networkinterface (923) to verify or access information associated a mobiledevice. Network interface (923) can be implemented as a wired interfacesuch as an Ethernet port or as a wireless interface such as a wirelesstransceiver that can access a network wirelessly (e.g., using Wi-Fi orother wireless communication protocol).

FIG. 9C illustrates a system (930) for provisioning a mobile device(931) with digital wallet capabilities using kiosk (901). Mobile device(931) can be a newly purchased mobile device or can be an existingmobile device that a user already owns. In some embodiments, mobiledevice (931) may be preloaded with a digital wallet application, andkiosk (901) is used to load credentials onto the digital walletapplication of mobile device (931). In other embodiments, kiosk (901)can be used to load a digital wallet application along with personalizedcredentials onto mobile device (931) if mobile device (931) does notinclude a preloaded digital wallet application.

According to some embodiments, kiosk (901) is communicatively coupled toa trusted service manager (TSM) (933), for example, via a network (932).TSM (933) offers services to support contactless transaction servicesthat are performed with mobile devices. The basic functionalities thatmay be provided by the TSM (933) include the ability to manage securitykeys or tokens that are used to access a mobile device's secure element(SE) chip (e.g., a secure memory chip or a secured partition of amemory) in which credentials of a digital wallet application can bestored. The SE is used by the mobile device (931) to host and store dataand applications that require a high degree of security. The SE can beprovided to the mobile device (931), for example, by an entity of thepayment processing network such as an issuer of a credit card, by acontactless transaction service provider, by a mobile network operator(MNO), by a mobile device manufacturer, or by other suitable entities.Access to the SE of mobile device (931) can be achieved by obtaining theproper security key or token from the SE provider.

Although TSM (933) is shown as a separate entity, in some embodiments,TSM (933) may be integrated with issuer system (935) for activating andpersonalizing a digital wallet application with a user's credentials, orbe integrated with kiosk (901). Upon request, TSM (933) may obtain theproper security key or token from a SE provider to lock or unlock the SEon mobile device (931), for example, to allow kiosk (901) to load usercredentials onto the SE of mobile device (931).

Provisioning of mobile device (931) for digital wallet capabilities maybe initiated when a user engages kiosk (901) by providing user input toa user input interface of kiosk (901), for example, by touching a touchscreen of kiosk (901) or by pressing a key on a keyboard of kiosk (901),etc. Upon user engagement, kiosk (901) may provide visual and/or audioinstructions for the user to complete the provisioning process. Forexample, kiosk (901) may display a message instructing the user tocommunicatively connect the user's mobile device (931) to kiosk (901).

To communicatively connect the user's mobile device (931) to kiosk(901), a user can physically connect mobile device (931) to the mobiledevice interface (e.g., a connector or cable) of kiosk (901) for a wiredcommunication channel, or by placing mobile device (931) in closeproximity to the mobile device interface (e.g., wireless transceiver) ofkiosk (901) to allow an ad hoc wireless communication channel to beestablished between mobile device (931) and kiosk (901). The ad hocwireless communication channel can be established via NFC, RF,Bluetooth, Wi-Fi, or other suitable wireless communication protocols. Insome embodiments, when kiosk (901) senses a mobile device (931) is inclose proximity, kiosk (901) may display a message asking to ask if theuser grants permission for kiosk (901) to establish a wirelesscommunication channel with mobile device (931).

Once a communication channel (wired or wireless) is established betweenmobile device (931) and kiosk (901), kiosk (901) may provide furthervisual and/or audio instructions to the user to present a credentialstorage instrument (905) to continue with the digital walletprovisioning process. For example, kiosk (901) may instruct the user toplace credential storage instrument (905) in physical contact with thecredential storage instrument reader of kiosk (901) (e.g., by swiping orinserting a magnetic stripe card into a magnetic stripe reader, or byinserting a chip-card into a chip-card reader slot), or to placecredential storage instrument (905) in close proximity with thecredential storage instrument reader of kiosk (901) (e.g., by placing acontactless card in close proximity to a contactless card reader, or byplacing a printed medium with a bar code or OR code in front of aninfrared scanner). Upon presenting credential storage instrument (905)to the credential storage instrument reader of kiosk (901), kiosk (901)accesses the credential storage instrument (905) to read usercredentials from credential storage instrument (905).

It should be noted that although in the above process, a communicationchannel between mobile device (931) and kiosk (901) is established firstbefore a credential storage instrument is presented to kiosk (901), insome embodiments, a credential storage instrument can be presented tokiosk (901) prior to communicatively connecting mobile device (931) tokiosk (901). Furthermore, in addition to providing user input on theuser input interface of kiosk (901) to initiate the process, the digitalwallet provisioning process can alternatively be initiated by simplycommunicatively connecting mobile device (931) to kiosk (901) or bypresenting a credential storage instrument to kiosk (901).

Once kiosk (901) has retrieve user credentials from credential storageinstrument (905), kiosk (901) may carry out a verification process toconfirm that the user is authorized to provision mobile device (931)with credentials from credential storage instrument (905). In someembodiments, the verification process may be carried out by kiosk (901)without requiring any additional user input. For example, kiosk (901)may retrieve a mobile phone number and/or a mobile device identifierfrom mobile device (931) that can be used to look up the mobilesubscriber name associated with mobile device (931) from mobile networkoperator (936). Kiosk (901) may also retrieve the name on credentialstorage instrument (905), or look up the name associated with thecredential storage instrument (905) using credentials retrieved fromcredential storage instrument (905) by contacting issuer system (935).If the mobile subscriber name matches the user name of the credentialstorage instrument (905), it can be assumed that the user is the properowner of both mobile device (931) and credential storage instrument(905), and that the user is authorized to provision mobile device (931)with credentials from credential storage instrument (905).

It should be noted that embodiments of the present invention provide amore secure method of provisioning mobile device (931) as compared tosome over-the-air (OTA) provisioning processes, because credentialstorage instrument (905) is in physical possession of the user duringthe kiosk provisioning process. This can prevent, for example, afraudulent user from provisioning a mobile device with stolencredentials when the fraudulent user does not have physical possessionof the credential storage instrument.

In some embodiments, for additional security, before proceeding furtherwith the provisioning process, kiosk (901) may request the user to entera PIN number associated with credential storage instrument (905) toauthenticate the user. Kiosk (901) may alternatively or additionallyrequest the user to login to an online account provided by an issuer ofthe credential storage instrument (905) via a web-enable browser, and/orrequest the user to login to an online account provided by the mobilenetwork operator of mobile device (931).

After kiosk (901) determines that the user is authorized to provisionmobile device (931) with credentials from credential storage instrument(905), kiosk (901) may send a registration or activation request to TSM(933). In some embodiments, the registration or activation request issent with the appropriate personalization data (e.g., credentialsretrieved from credential storage instrument (905)). TSM (933) mayprocess the registration or activation request by personalizing adigital wallet application with the appropriate personalization data,unlock the SE of mobile device (931), and providing the personalizeddigital wallet application to kiosk (901) for download to mobile device(931). In some embodiments, for example, in which mobile device (931)includes a preload digital wallet application, TSM (933) may process therequest by unlocking the SE of mobile device (931) to allow kiosk (901)to transfer credentials retrieved from credential storage instrument(905) onto the SE of mobile device (931). According to some embodiments,some or all of the functionality performed by TSM (9) can be integratedinto kiosk (901).

Depending on the type of credential storage instrument (905) being used,additional credentials that are not stored on credential storageinstrument (905), or additional credentials that cannot be read by thecredential storage instrument reader of kiosk (901) may be needed toenable mobile device (931) to perform contactless transactions. Forexample, if credential storage instrument (905) is a credit card, adynamic card verification value (dCVV) may be required to conductcontactless payment transactions carried out by mobile device (931). Insuch embodiments, during the digital wallet provisioning process, kiosk(901) may send a registration or activation request to issuer system(935) to obtain additional credentials such as a dCVV software that canbe used by mobile device (931) to generate a dCVV when performingcontactless payment transactions. The additional credentials (e.g., dCVVsoftware) obtained from issuer system (935) can be stored in SE ofmobile device (931) along with credentials retrieved from credentialstorage instrument (905) during the digital wallet provisioning process.In some embodiments, the credentials retrieved from credential storageinstrument (905) may also be modified or augmented by issuer system(935) before being stored in mobile device (931). Credentials loadedinto the SE of mobile device (931) by kiosk (901) may also use dataencryption standards such as, e.g., RSA with a key of at least 1024bits, triple data encryption standard (DES), 128-bit advanced encryptionstandard (AES), an RC4 stream encryption algorithm using minimum 128-bitkey length, etc.

Once credentials from credential storage instrument (905) has beenloaded onto a digital wallet application of mobile device (931), kiosk(901) may provide visual and/or audio instructions asking the user ifthe user wishes to load credentials from addition credential storageinstruments onto mobile device (931). If so, the process described abovecan be repeated for each credential storage instrument. In someembodiments, the credential storage instruments can be processed inbatch mode. For example, kiosk (901) may allow a user to swipe multiplecredential storage instruments first before kiosk (901) begins loadingthe respective credentials onto mobile device (931). Credentials fromthe multiple credential storage instruments can be stored temporarily inkiosk (901), and once the user has presented the desired number ofcredential storage instruments to kiosk (901), kiosk (901) then beginsthe provisioning process of loading the credentials onto mobile device(931).

According to some embodiments, kiosk (901) can also be used to transfercredentials from one digital wallet application to another. For example,when a user purchases a new mobile device, the user may already have apersonalized digital wallet application on the user's old mobile device.The user may want to transfer the credentials stored on the old mobiledevice to the new one. Instead of presenting individual credentialstorage instruments for kiosk (901) to read, the user may place theuser's old mobile device in close proximity to the credential storageinstrument reader of kiosk (901). Kiosk (901) may then access thedigital wallet application stored on the old mobile device to retrievethe credentials stored therein. After retrieving the credentials fromthe old mobile device, kiosk (901) can provision the new mobile devicewith the retrieved credentials using the process described above.

In addition to or as an alternative to provisioning mobile device (931),kiosk (901) may also load credentials into a cloud-based digital wallet(934). Cloud-based digital wallet (934) allows credentials to be storedin network-accessible storage that is external to mobile device (931).Using cloud-based digital wallet (934) has the advantage that once thecredentials have been loaded to cloud-based digital wallet (934), theuser can avoid having to transfer the credentials to a new mobile deviceeach time the user switches mobile devices. Thus, in some embodiments, auser may use kiosk (901) to load credentials from credential storageinstruments into cloud-based digital wallet (934) without the presenceof a mobile device.

In some embodiments, kiosk (901) may perform additional digital walletmanagement functions. For example, once the digital wallet applicationon mobile device (931) has been provisioned and personalized, kiosk(901) may allow a user to purchase digital media for mobile device (931)using credentials loaded onto the digital wallet application. Kiosk(901) may also allow a user to deposit or add value into accountsassociated with the credentials stored in the digital walletapplication. For example, kiosk (901) may allow the user to add value toa transit fare account stored in the digital wallet application.However, it should be note that these additional functions are differentfrom the digital wallet provisioning process in that these additionalfunctions required the digital wallet application to have the necessarycredentials before these functions can be performed. In contrast, theprovisioning process described herein is used to provide the mobiledevice with credentials that the digital wallet application lacked priorto being provisioned by kiosk (901). Kiosks according to embodiments ofthe invention may or may not provide the aforementioned additionalfunctions.

FIG. 9D illustrates a flow diagram of a method (950) performed by akiosk or other suitable computing devices for provisioning a digitalwallet application of a mobile device according to some embodiments. Atblock (951), a communication channel is established between a user'smobile device. The communication channel can be a wired connection or awireless connection as described above. At block (952), a credentialstorage instrument such as a magnetic stripe card, a chip card, or othercredential storage instruments described above is accessed to retrievecredentials stored in the credential storage instrument. At block (953),it is determined whether the user is authorized to provision a digitalwallet application for the mobile device with the retrieved credentials.This determination can be made according to any of the processesdescribed above. If it is determined that the user is not authorized, atblock (956), the process is terminated without provisioning the mobiledevice. If it is determined that the user is authorized, then at block(954), a request is made to unlock the secure element (SE) of the mobiledevice. The SE may be unlocked with a security key or token provided bya TSM or by a kiosk with integrated TSM functionality. Once the SE ofthe mobile device is unlocked, a digital wallet application for themobile device is provisioned by loading the user credentials retrievedfrom the credential storage instrument into the SE. In some embodiments,the user credentials may be modified, augmented (e.g., with a CVV2),and/or encrypted before being stored into the SE of the mobile device.Method (950) can be repeated for multiple credential storageinstruments. Subsequent to the provisioning process, the SE of mobiledevice is locked to prevent unauthorized access.

It should be understood that method (950) for provisioning a digitalwallet application of a mobile device can include additional operationsthat are not depicted in FIG. 9D, or may include less operations inother embodiments. Furthermore, some of the operations may be performedin a different order than what is depicted.

FIG. 10 shows a swim-lane flow diagram illustrating the flow between amobile device (931), a kiosk (901), and a remotely accessible serversuch as a payment credentials issuer (935) or a TSM (933) according toembodiments.

A consumer may present (1001) his portable payment device or credentialstorage instrument (for example, a payment card) at the kiosk which mayextract payment credentials from the portable payment device. Forexample, the consumer may insert his payment card into a kiosk and a“credential transfer” transaction may be requested. The consumer may beprompted for his payment card PIN which may be entered into the kioskvia a keypad. The consumer may also provide (1002) an identifier, forexample, the kiosk may also prompt the consumer for an “alias” which isused as an identifier for the consumer and his mobile device.

The kiosk may connect (1003) to the consumer's mobile device aspreviously described to establish (1004) a connection. The kiosk may usethe consumer's provided identifier to identify the mobile device forconnection, for example, if this is in a contactless manner.

The kiosk may send (1005) an activation request to a remotely accessibleserver provided by a TSM in order to obtain authorization to store thepayment credentials at the secure element associated with the mobiledevice and also to unlock the secure element. The activation request mayuse the identifier provided by the consumer which may be registered forthe consumer's mobile device and/or secure element and the identifiermay be used to identify (1006) the mobile device and its secure element.The TSM may unlock (1007/1008) the secure element associated with themobile device.

The payment credentials may be provisioned (1009/1010) to the secureelement of the mobile device using the connection to the kiosk. Thesemay be provisioned securely to the secure element.

Additional credentials that are not stored on the portable paymentdevice may be needed to also be stored at the secure element to enablethe mobile device to perform contactless transactions. For example, adynamic card verification value (dCVV) may be required to conductcontactless payment transactions carried out by mobile device. In suchembodiments, the kiosk may send a registration request (1011) to aremotely accessible server of an issuer system to obtain additionalcredentials. The identifier may be included in the request and used bythe remotely accessible server to identify (1012) the correct additionalcredentials. The additional credentials may be, in one example, dCVVsoftware that can be used by mobile device to generate a dCVV whenperforming contactless payment transactions. The registration requestmay include the identifier provided by the consumer in order to obtainthe correct additional credentials for the consumer's portable paymentdevice.

The additional credentials (e.g., dCVV software) obtained from issuersystem can transmitted (1013/1014) to and stored in the secure elementassociated with the mobile device along with payment credentialsretrieved from the kiosk during the digital wallet provisioning process.Alternatively, the additional credentials may be communicated directlyto the secure element of the mobile device.

FIG. 11 illustrates an example of a computing device (1100) in whichvarious aspects of the disclosure may be implemented. The computingdevice (1100) may be suitable for storing and executing computer programcode. The various participants and elements in the previously describedsystem diagrams may use any suitable number of subsystems or componentsof the computing device (1100) to facilitate the functions describedherein.

The computing device (1100) may include subsystems or componentsinterconnected via a communication infrastructure (1105) (for example, acommunications bus, a cross-over bar device, or a network). Thecomputing device (1100) may include at least one central processor(1110) and at least one memory component in the form ofcomputer-readable media.

The memory components may include system memory (1115), which mayinclude read only memory (ROM) and random access memory (RAM). A basicinput/output system (BIOS) may be stored in ROM. System software may bestored in the system memory (1115) including operating system software.

The memory components may also include secondary memory (1120). Thesecondary memory (1120) may include a fixed disk (1121), such as a harddisk drive, and, optionally, one or more removable-storage interfaces(1122) for removable-storage components (1123).

The removable-storage interfaces (1122) may be in the form ofremovable-storage drives (for example, magnetic tape drives, opticaldisk drives, floppy disk drives, etc.) for corresponding removablestorage-components (for example, a magnetic tape, an optical disk, afloppy disk, etc.), which may be written to and read by theremovable-storage drive.

The removable-storage interfaces (1122) may also be in the form of portsor sockets for interfacing with other forms of removable-storagecomponents (1123) such as a flash memory drive, external hard drive, orremovable memory chip, etc.

The computing device (1100) may include an external communicationsinterface (1130) for operation of the computing device (1100) in anetworked environment enabling transfer of data between multiplecomputing devices (1100). Data transferred via the externalcommunications interface (1130) may be in the form of signals, which maybe electronic, electromagnetic, optical, radio, or other types ofsignal.

The external communications interface (1130) may enable communication ofdata between the computing device (1100) and other computing devicesincluding servers and external storage facilities. Web services may beaccessible by the computing device (1100) via the communicationsinterface (1130).

The external communications interface (1130) may also enable other formsof communication to and from the computing device (1100) including,voice communication, near field communication, Bluetooth, etc.

The computer-readable media in the form of the various memory componentsmay provide storage of computer-executable instructions, datastructures, program modules, and other data. A computer program productmay be provided by a computer-readable medium having storedcomputer-readable program code executable by the central processor(1110).

A computer program product may be provided by a non-transientcomputer-readable medium, or may be provided via a signal or othertransient means via the communications interface (1130).

Interconnection via the communication infrastructure (1105) allows acentral processor (1110) to communicate with each subsystem or componentand to control the execution of instructions from the memory components,as well as the exchange of information between subsystems or components.

Peripherals (such as printers, scanners, cameras, or the like) andinput/output (I/O) devices (such as a mouse, touchpad, keyboard,microphone, joystick, or the like) may couple to the computing device(1100) either directly or via an I/O controller (1135). These componentsmay be connected to the computing device (1100) by any number of meansknown in the art, such as a serial port.

One or more monitors (1145) may be coupled via a display or videoadapter (1140) to the computing device (1100).

FIG. 12 shows a block diagram of a communication device (1200) that maybe used in embodiments of the disclosure. The communication device(1200) may be a cell phone, a feature phone, a smart phone, a satellitephone, or a computing device having a phone capability.

The communication device (1200) may include a processor (1205) (e.g., amicroprocessor) for processing the functions of the communication device(1200) and a display (1220) to allow a user to see the phone numbers andother information and messages. The communication device (1200) mayfurther include an input element (1225) to allow a user to inputinformation into the device (e.g., input buttons, touch screen, etc.), aspeaker (1230) to allow the user to hear voice communication, music,etc., and a microphone (1235) to allow the user to transmit his or hervoice through the communication device (1200).

The processor (1210) of the communication device (1200) may connect to amemory (1215). The memory (1215) may be in the form of acomputer-readable medium that stores data and, optionally,computer-executable instructions. The memory (1215).

The communication device (1200) may also include a communication element(1240) for connection to communication channels (e.g., a cellulartelephone network, data transmission network, Wi-Fi network,satellite-phone network, Internet network, Satellite Internet Network,etc.). The communication element (1240) may include an associatedwireless transfer element, such as an antenna.

The communication element (1240) may include a subscriber identitymodule (SIM) in the form of an integrated circuit that stores aninternational mobile subscriber identity and the related key used toidentify and authenticate a subscriber using the communication device(1200). One or more subscriber identity modules may be removable fromthe communication device (1200) or embedded in the communication device(1200).

The communication device (1200) may further include a contactlesselement (1250), which is typically implemented in the form of asemiconductor chip (or other data storage element) with an associatedwireless transfer element, such as an antenna. The contactless element(1250) may be associated with (e.g., embedded within) the communicationdevice (1200) and data or control instructions transmitted via acellular network may be applied to the contactless element (1250) bymeans of a contactless element interface (not shown). The contactlesselement interface may function to permit the exchange of data and/orcontrol instructions between mobile device circuitry (and hence thecellular network) and the contactless element (1250).

The contactless element (1250) may be capable of transferring andreceiving data using a near field communications (NFC) capability (ornear field communications medium) typically in accordance with astandardized protocol or data transfer mechanism (e.g., ISO 14443/NFC).Near field communications capability is a short-range communicationscapability, such as radio-frequency identification (RFID), Bluetooth,infra-red, or other data transfer capability that can be used toexchange data between the communication device (1200) and aninterrogation device. Thus, the communication device (1200) may becapable of communicating and transferring data and/or controlinstructions via both a cellular network and near field communicationscapability.

Communication devices (1200) that support mobile contactless paymentstypically support contactless transactions using the EMV contactlesscommunication protocol (EMV-CCP), which is based on ISO 14443, in orderto interact with merchant access devices. This capability is typicallymet by implementing NFC. The NFC capability on communication device(1200) might be enabled by an embedded NFC chip or by the addition of anexternal memory card or accessory that contains the NFC chip.Additionally, communication device (1200) typically includes a secureelement (SE) (1260) either embedded in the handset or in the subscriberidentity module (SIM) card. The SE (1260) can also be included in anadd-on device such as a micro-Secure Digital (microSD) card, or anexpansion component for adding to a communication component of thecommunication device (1200).

The data stored in the memory (1215) may include: operation datarelating to the operation of the communication device (1200), personaldata (e.g., name, date of birth, identification number, etc.), financialdata (e.g., bank account information, a bank identification number(BIN), credit or debit card number information, account balanceinformation, expiration date, loyalty provider account numbers, etc.),transit information (e.g., as in a subway or train pass), accessinformation (e.g., as in access badges), etc. A user may transmit thisdata from the communication device (1200) to selected receivers.

The communication device (1200) may be, amongst other things, anotification device that can receive alert messages and access reports,a portable merchant device that can be used to transmit control dataidentifying a discount to be applied, as well as a portable consumerdevice that can be used to make payments.

The foregoing description of the embodiments of the invention has beenpresented for the purpose of illustration; it is not intended to beexhaustive or to limit the invention to the precise forms disclosed.Persons skilled in the relevant art can appreciate that manymodifications and variations are possible in light of the abovedisclosure.

Some portions of this description describe the embodiments of theinvention in terms of algorithms and symbolic representations ofoperations on information. These algorithmic descriptions andrepresentations are commonly used by those skilled in the dataprocessing arts to convey the substance of their work effectively toothers skilled in the art. These operations, while describedfunctionally, computationally, or logically, are understood to beimplemented by computer programs or equivalent electrical circuits,microcode, or the like. The described operations may be embodied insoftware, firmware, hardware, or any combinations thereof.

The software components or functions described in this application maybe implemented as software code to be executed by one or more processorsusing any suitable computer language such as, for example, Java, C++, orPerl using, for example, conventional or object-oriented techniques. Thesoftware code may be stored as a series of instructions, or commands ona non-transitory computer-readable medium, such as a random accessmemory (RAM), a read-only memory (ROM), a magnetic medium such as ahard-drive or a floppy disk, or an optical medium such as a CD-ROM. Anysuch computer-readable medium may also reside on or within a singlecomputational apparatus, and may be present on or within differentcomputational apparatuses within a system or network.

Any of the steps, operations, or processes described herein may beperformed or implemented with one or more hardware or software modules,alone or in combination with other devices. In one embodiment, asoftware module is implemented with a computer program productcomprising a non-transient computer-readable medium containing computerprogram code, which can be executed by a computer processor forperforming any or all of the steps, operations, or processes described.

Finally, the language used in the specification has been principallyselected for readability and instructional purposes, and it may not havebeen selected to delineate or circumscribe the inventive subject matter.It is therefore intended that the scope of the invention be limited notby this detailed description, but rather by any claims that issue on anapplication based hereon. Accordingly, the disclosure of the embodimentsof the invention is intended to be illustrative, but not limiting, ofthe scope of the invention, which is set forth in the following claims.

1.-30. (canceled)
 31. A method comprising the steps of: storing, by amobile device or a secure element associated with the mobile device, adecryption key; receiving, by the mobile device or the secure elementassociated with the mobile device from a remote server computer, arequest for the decryption key; and providing, by the mobile device tothe remote server computer, the decryption key, wherein the remoteserver computer decrypts encrypted payment credentials stored by theremote server computer to form decrypted payment credentials, andtransmits the decrypted payment credentials to a receiving device. 32.The method of claim 31, further comprising: storing the encryptedpayment credentials at the remote server computer.
 33. The method ofclaim 31, wherein the remote server computer further communicatesadditional credentials to the receiving device, wherein the additionalcredentials are required in use in addition to the decrypted paymentcredentials or derivation of the decrypted payment credentials to carryout a transaction.
 34. The method of claim 31, wherein the secureelement is one of the group of: a secure element provided in the mobiledevice, a secure element embedded in a layer which sits between acommunication component of the mobile device and a communicationcomponent interface of the mobile device, a secure element provided in acommunication component of the mobile device, and a cloud-based secureelement associated with the mobile device.
 35. The method of claim 31,wherein the decrypted payment credentials comprise a PAN.
 36. The methodof claim 31, wherein the decrypted payment credentials are transmittedto the receiving device in a single secure transaction message.
 37. Themethod of claim 31, wherein the method further includes: determiningwhether or not the mobile device or the secure element corresponding toa personal identifier has been registered with the remote servercomputer.
 38. The method of claim 31, wherein the decrypted paymentcredentials are also on a portable payment device used by a user of themobile device.
 39. A mobile device comprising: a processor; and acomputer readable medium, the computer readable medium comprising code,executable by the processor for implementing a method comprising:storing, by the mobile device, a decryption key, receiving, by themobile device from a remote server computer, a request for thedecryption key; and providing, by the mobile device to the remote servercomputer, the decryption key, wherein the remote server computerdecrypts encrypted payment credentials stored by the remote servercomputer to form decrypted payment credentials, and transmits thedecrypted payment credentials to a receiving device.
 40. The mobiledevice of claim 39, wherein the method further comprises: storing theencrypted payment credentials at the remote server computer.
 41. Themobile device of claim 39, wherein the remote server computer furthercommunicates additional credentials to the receiving device, wherein theadditional credentials are required in use in addition to the decryptedpayment credentials or derivation of the decrypted payment credentialsto carry out a transaction.
 42. The mobile device of claim 39, whereinthe mobile device comprises a secure element, the secure element is oneof the group of: a secure element provided in the mobile device, asecure element embedded in a layer which sits between a communicationcomponent of the mobile device and a communication component interfaceof the mobile device, a secure element provided in a communicationcomponent of the mobile device, and a cloud-based secure elementassociated with the mobile device.
 43. The mobile device of claim 39,wherein the decrypted payment credentials comprise a PAN.
 44. The mobiledevice of claim 39, wherein the decrypted payment credentials aretransmitted to the receiving device in a single secure transactionmessage.
 45. The mobile device of claim 39, wherein the method furtherincludes: determining whether or not the mobile device corresponding toa personal identifier has been registered with the remote servercomputer.
 46. The mobile device of claim 39, wherein the decryptedpayment credentials are also on a portable payment device used by a userof the mobile device.
 47. A secure element associated with a mobiledevice, the secure element comprising: a computer readable medium, thecomputer readable medium comprising code, executable by a processor forimplementing a method comprising: storing, by the secure elementassociated with the mobile device, a decryption key, receiving, thesecure element associated with the mobile device from a remote servercomputer, a request for the decryption key; and providing, by the secureelement to the remote server computer, the decryption key, wherein theremote server computer decrypts encrypted payment credentials stored bythe remote server computer to form decrypted payment credentials, andtransmits the decrypted payment credentials to a receiving device. 48.The secure element of claim 47, wherein the method further comprises:storing the encrypted payment credentials at the remote server computer.49. The secure element of claim 47, wherein the remote server computerfurther communicates additional credentials to the receiving device,wherein the additional credentials are required in use in addition tothe decrypted payment credentials or derivation of the decrypted paymentcredentials to carry out a transaction.
 50. The secure element of claim47, wherein the secure element is one of the group of: a secure elementprovided in the mobile device, a secure element embedded in a layerwhich sits between a communication component of the mobile device and acommunication component interface of the mobile device, a secure elementprovided in a communication component of the mobile device, and acloud-based secure element associated with the mobile device.